负责人 <Select> does not spread usersSelectProps, so you lose useSelect-provided props like loading state, search handlers, and any configured filtering/pagination behavior. Consider spreading {...usersSelectProps} (and overriding options with your custom userOptions), to keep behavior consistent with other useSelect usages.

taskStages memo returns { unassignedStage, stages: [] } in the empty state but the non-empty state returns { unassignedStage, columns: grouped }. Downstream JSX reads taskStages.columns, so when filteredTasks is empty (e.g. filters exclude all tasks) stage columns disappear entirely. Return a consistent shape (use columns in both branches), and avoid early-returning on !filteredTasks.length so the board can still render all stages with zero tasks.

In the 阶段 <Select>, {...stagesSelectProps} is spread after value/onChange, so any value/onChange from stagesSelectProps will override your controlled state and handleStageChange (this pattern typically breaks filter updates). Spread stagesSelectProps first and then override with value={filters.stageIds} / onChange={handleStageChange}. Also consider adding an explicit "未分配"/"Unassigned" option (value "unassigned") if you want users to be able to filter the unassigned column.

dayjs is imported but never used in this component (only Dayjs is used as a type). Remove the unused default import to avoid lint/TS warnings (or switch to import type { Dayjs } from 'dayjs' if your tooling supports it).

userOptions builds avatarUrl via (user as any).avatarUrl, but useSelect().selectProps.options typically only contains { value, label }, so avatars will likely always be undefined and the any cast hides it. Prefer mapping from the useSelect queryResult.data?.data nodes (which include avatarUrl in USERS_SELECT_QUERY) to build options with strongly typed fields, similar to the pattern used elsewhere when rendering SelectOptionWithAvatar.